Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ea91e44ee04e6e7bcd10960c3683317682be7607f71d585c9ac389a42f8da96b

Tx prefix hash: 804e88abc7cc313dea6ae1c2b51cfc3f0b866524934d81a02d25f6f1b004f816
Tx public key: f23baab5078f1445803aca5585de85a94c3b81e12ea3f832ec8a453c4750a9a3
Timestamp: 1731494337 Timestamp [UCT]: 2024-11-13 10:38:57 Age [y:d:h:m:s]: 00:212:18:32:48
Block: 1152758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151859 RingCT/type: yes/0
Extra: 01f23baab5078f1445803aca5585de85a94c3b81e12ea3f832ec8a453c4750a9a30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7f8b146bebd87b71dc930468f04e15bd444acd3b5ce241b15bd263592f78fb1 0.600000000000 1638361 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1152768, "vin": [ { "gen": { "height": 1152758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7f8b146bebd87b71dc930468f04e15bd444acd3b5ce241b15bd263592f78fb1" } } ], "extra": [ 1, 242, 59, 170, 181, 7, 143, 20, 69, 128, 58, 202, 85, 133, 222, 133, 169, 76, 59, 129, 225, 46, 163, 248, 50, 236, 138, 69, 60, 71, 80, 169, 163, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8