Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcfb3be12bbacd898e38d537ed3dd99633b6ee31af8c6e87f6b3e22a2667543f

Tx prefix hash: afa68b394b489181ad44880a8ae9effc591ae89bf71c3b9d24839c0c49e2cd83
Tx public key: af21b3008be87f712cbc0fbaf40682b84da73fc6e4f22f2ff695e2a875d5d57a
Timestamp: 1705114156 Timestamp [UCT]: 2024-01-13 02:49:16 Age [y:d:h:m:s]: 01:306:16:45:12
Block: 934117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478040 RingCT/type: yes/0
Extra: 01af21b3008be87f712cbc0fbaf40682b84da73fc6e4f22f2ff695e2a875d5d57a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeffeb97975e97971a130bf445a14a806b231463c8b4b0e5f944f2a3cbf08a5f 0.600000000000 1392105 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": 934127, "vin": [ { "gen": { "height": 934117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeffeb97975e97971a130bf445a14a806b231463c8b4b0e5f944f2a3cbf08a5f" } } ], "extra": [ 1, 175, 33, 179, 0, 139, 232, 127, 113, 44, 188, 15, 186, 244, 6, 130, 184, 77, 167, 63, 198, 228, 242, 47, 47, 246, 149, 226, 168, 117, 213, 213, 122, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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