Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0db893c29e1cce26905f4351ffe3afdbfb9c105d9be4dd6f382586729a79ade

Tx prefix hash: fbb35573d8fe8af9ef68d2bf7807379f1adb3a0e12c26f48d25e45ad72a4ef01
Tx public key: a536ff988ab0faab8daf2b104a6e3d4632982b1a41cdaabc10c358053e12f22a
Timestamp: 1672952135 Timestamp [UCT]: 2023-01-05 20:55:35 Age [y:d:h:m:s]: 02:010:02:13:57
Block: 668375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529111 RingCT/type: yes/0
Extra: 01a536ff988ab0faab8daf2b104a6e3d4632982b1a41cdaabc10c358053e12f22a02110000000533af99f4000000000000000000

1 output(s) for total of 3.744519779000 dcy

stealth address amount amount idx
00: 09eb91d14dcf7f18f7688b6e1bfe654444911a984ebf8e9d52dd56532f2b7e6a 3.744519779000 1109620 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": 668385, "vin": [ { "gen": { "height": 668375 } } ], "vout": [ { "amount": 3744519779, "target": { "key": "09eb91d14dcf7f18f7688b6e1bfe654444911a984ebf8e9d52dd56532f2b7e6a" } } ], "extra": [ 1, 165, 54, 255, 152, 138, 176, 250, 171, 141, 175, 43, 16, 74, 110, 61, 70, 50, 152, 43, 26, 65, 205, 170, 188, 16, 195, 88, 5, 62, 18, 242, 42, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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