Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e4676ceb27e43c150aaec76836102f18dbb516182451169df6ef935a01ae24a

Tx prefix hash: 39d4bb966b7a5e2a711244d9e11bf2112945c7ee535f3125a78e6ade5cdf48a6
Tx public key: 3591221d4fe1dcbbe1bfd13420850f8b9770b02601938bc804b9cfc7f5fe5c2c
Timestamp: 1722616152 Timestamp [UCT]: 2024-08-02 16:29:12 Age [y:d:h:m:s]: 00:161:03:33:26
Block: 1079249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115284 RingCT/type: yes/0
Extra: 013591221d4fe1dcbbe1bfd13420850f8b9770b02601938bc804b9cfc7f5fe5c2c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a19e1ae65b25fa6fdf590563d4a0895772eec544d2f14deb852ce31413a3a848 0.600000000000 1552118 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": 1079259, "vin": [ { "gen": { "height": 1079249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a19e1ae65b25fa6fdf590563d4a0895772eec544d2f14deb852ce31413a3a848" } } ], "extra": [ 1, 53, 145, 34, 29, 79, 225, 220, 187, 225, 191, 209, 52, 32, 133, 15, 139, 151, 112, 176, 38, 1, 147, 139, 200, 4, 185, 207, 199, 245, 254, 92, 44, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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