Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f8eb469d4f0b234703532d9a56a0ca107233517b998bf83512a7aa4bdae03e4

Tx prefix hash: 15c0a940a66a30f504c372097013d10ee9d82620fa5b3e3a6404f67a440e1106
Tx public key: e2db1775e0c989123f14c5ae1295b61ff14cf89dab1ce0238c805245f4b0a21b
Timestamp: 1715479339 Timestamp [UCT]: 2024-05-12 02:02:19 Age [y:d:h:m:s]: 00:187:01:13:20
Block: 1020113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133849 RingCT/type: yes/0
Extra: 01e2db1775e0c989123f14c5ae1295b61ff14cf89dab1ce0238c805245f4b0a21b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b4ba4112aac21014075cc9a6bce35cb1563a6f0787ba377cdc38a50b91511c1 0.600000000000 1484172 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": 1020123, "vin": [ { "gen": { "height": 1020113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b4ba4112aac21014075cc9a6bce35cb1563a6f0787ba377cdc38a50b91511c1" } } ], "extra": [ 1, 226, 219, 23, 117, 224, 201, 137, 18, 63, 20, 197, 174, 18, 149, 182, 31, 241, 76, 248, 157, 171, 28, 224, 35, 140, 128, 82, 69, 244, 176, 162, 27, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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