Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbde511ff6b3730d64e248d0d6d088a4789548e29f1c92693137d33eb7a820ae

Tx prefix hash: 5005e789811e8a2fdda92c0817f20d4c94bac1cb742b6e94fcd22beff789c284
Tx public key: 7faad764362a1b4ddd4eb1b006ec09aabfea6c6e70c0737fdc3f7786e338f24e
Timestamp: 1685102178 Timestamp [UCT]: 2023-05-26 11:56:18 Age [y:d:h:m:s]: 02:165:13:15:46
Block: 768486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638100 RingCT/type: yes/0
Extra: 017faad764362a1b4ddd4eb1b006ec09aabfea6c6e70c0737fdc3f7786e338f24e02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.744564554000 dcy

stealth address amount amount idx
00: 4731a491d0e67596a069163ac46da936cbf5416b1120317193562942b6006f0f 1.744564554000 1217687 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": 768496, "vin": [ { "gen": { "height": 768486 } } ], "vout": [ { "amount": 1744564554, "target": { "key": "4731a491d0e67596a069163ac46da936cbf5416b1120317193562942b6006f0f" } } ], "extra": [ 1, 127, 170, 215, 100, 54, 42, 27, 77, 221, 78, 177, 176, 6, 236, 9, 170, 191, 234, 108, 110, 112, 192, 115, 127, 220, 63, 119, 134, 227, 56, 242, 78, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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