Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f929bd48373451ef102df10756597e54100b4af10ac82dbeb77ff8f6e68c5bb6

Tx prefix hash: 4748564814c74169d940f861db44d844a5f2cf4dee3f4e1b33d9a2c1aa7f75cf
Tx public key: cabf7b6be9a912f20d79825baf3ef85052628d268e1fe5721305d07ac10ff0b1
Timestamp: 1617171574 Timestamp [UCT]: 2021-03-31 06:19:34 Age [y:d:h:m:s]: 03:269:06:56:15
Block: 230224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 951958 RingCT/type: yes/0
Extra: 01cabf7b6be9a912f20d79825baf3ef85052628d268e1fe5721305d07ac10ff0b1021100000097218d0d3b000000000000000000

1 output(s) for total of 105.969391294000 dcy

stealth address amount amount idx
00: a995a0906bd6df77adb665dc2c2015fad08d267f7f7059bb6bbc064291c93e8f 105.969391294000 477816 of 0

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": 230234, "vin": [ { "gen": { "height": 230224 } } ], "vout": [ { "amount": 105969391294, "target": { "key": "a995a0906bd6df77adb665dc2c2015fad08d267f7f7059bb6bbc064291c93e8f" } } ], "extra": [ 1, 202, 191, 123, 107, 233, 169, 18, 242, 13, 121, 130, 91, 175, 62, 248, 80, 82, 98, 141, 38, 142, 31, 229, 114, 19, 5, 208, 122, 193, 15, 240, 177, 2, 17, 0, 0, 0, 151, 33, 141, 13, 59, 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