Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb9aaccf0f4884888a3872ac71a66dff1e2cf5708a9a01af7f22a8443cdefd79

Tx prefix hash: ebd2b445cbc62bcb8f0eec9526f9a65b47734060394dbc17ec1c1bf341588a8e
Tx public key: 2866fdfc982ea4b1045e42fa0fd000b4f8271e45bbb4df54b679c7e325d5b91a
Timestamp: 1695950006 Timestamp [UCT]: 2023-09-29 01:13:26 Age [y:d:h:m:s]: 01:102:10:03:36
Block: 858374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334468 RingCT/type: yes/0
Extra: 012866fdfc982ea4b1045e42fa0fd000b4f8271e45bbb4df54b679c7e325d5b91a021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.878720290000 dcy

stealth address amount amount idx
00: 03301fcbed3eb230e56e5ce220e99f6bfd7d8a447d16795d3c78e5f2715620cf 0.878720290000 1312546 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": 858384, "vin": [ { "gen": { "height": 858374 } } ], "vout": [ { "amount": 878720290, "target": { "key": "03301fcbed3eb230e56e5ce220e99f6bfd7d8a447d16795d3c78e5f2715620cf" } } ], "extra": [ 1, 40, 102, 253, 252, 152, 46, 164, 177, 4, 94, 66, 250, 15, 208, 0, 180, 248, 39, 30, 69, 187, 180, 223, 84, 182, 121, 199, 227, 37, 213, 185, 26, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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