Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56359dc89647d5e832533e6a365fd7cdd244bcf108e3917c6f968a26444ab144

Tx prefix hash: 3fd2f11067c5a25e27439c01077dc22bdd89c3caad57fa76e4f28337cd57efb7
Tx public key: e85fde2d94a30fc83068be13ecafb88369290ac00dbb47edfd0f1bd75eb8041e
Timestamp: 1682317365 Timestamp [UCT]: 2023-04-24 06:22:45 Age [y:d:h:m:s]: 02:035:14:20:20
Block: 745394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547617 RingCT/type: yes/0
Extra: 01e85fde2d94a30fc83068be13ecafb88369290ac00dbb47edfd0f1bd75eb8041e021100000001e7ace25d000000000000000000

1 output(s) for total of 2.080656848000 dcy

stealth address amount amount idx
00: 4b521bf3190dc5de8fb2d99430aaf6e3a3c0d999973d5a51aa116f3bd7c0f34c 2.080656848000 1192841 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": 745404, "vin": [ { "gen": { "height": 745394 } } ], "vout": [ { "amount": 2080656848, "target": { "key": "4b521bf3190dc5de8fb2d99430aaf6e3a3c0d999973d5a51aa116f3bd7c0f34c" } } ], "extra": [ 1, 232, 95, 222, 45, 148, 163, 15, 200, 48, 104, 190, 19, 236, 175, 184, 131, 105, 41, 10, 192, 13, 187, 71, 237, 253, 15, 27, 215, 94, 184, 4, 30, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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