Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88b727323874145181ee979113e1061649a9ed7750aad99231047019dcf439c7

Tx prefix hash: f7aaf3772ed2f6fc48125d513d2668b2179b6e1a8ebad4eae470669a8c30a6fb
Tx public key: 6c4e01968ec85a6b6e5241cd44a59c75deec830e9cffc7f94ef64b8a1ff9b4ad
Timestamp: 1723138377 Timestamp [UCT]: 2024-08-08 17:32:57 Age [y:d:h:m:s]: 00:253:02:33:38
Block: 1083569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180796 RingCT/type: yes/0
Extra: 016c4e01968ec85a6b6e5241cd44a59c75deec830e9cffc7f94ef64b8a1ff9b4ad02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac31126ce74457d0dbb079aae202c5b1ef79d9d154802140685bbb82a8962f5b 0.600000000000 1557536 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": 1083579, "vin": [ { "gen": { "height": 1083569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac31126ce74457d0dbb079aae202c5b1ef79d9d154802140685bbb82a8962f5b" } } ], "extra": [ 1, 108, 78, 1, 150, 142, 200, 90, 107, 110, 82, 65, 205, 68, 165, 156, 117, 222, 236, 131, 14, 156, 255, 199, 249, 78, 246, 75, 138, 31, 249, 180, 173, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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