Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 994bca814719dd2d361b0e64f37365da6c78f2640bc472ce8cd6480f38aa666e

Tx prefix hash: 318f25c01b221c3591328d275015fc1233f32a271c0f99a6e31a83ce465d889c
Tx public key: e034af5ff4308399f236215cd2881e46ef6afd1e0018dd0a7264cb27437c4d4a
Timestamp: 1730474867 Timestamp [UCT]: 2024-11-01 15:27:47 Age [y:d:h:m:s]: 01:007:00:23:55
Block: 1144313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263435 RingCT/type: yes/0
Extra: 01e034af5ff4308399f236215cd2881e46ef6afd1e0018dd0a7264cb27437c4d4a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc8ab1201b3e0e36a662c35dbd07800e2d7474f6825c3bf59aec8b87ff18c1a5 0.600000000000 1628488 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": 1144323, "vin": [ { "gen": { "height": 1144313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc8ab1201b3e0e36a662c35dbd07800e2d7474f6825c3bf59aec8b87ff18c1a5" } } ], "extra": [ 1, 224, 52, 175, 95, 244, 48, 131, 153, 242, 54, 33, 92, 210, 136, 30, 70, 239, 106, 253, 30, 0, 24, 221, 10, 114, 100, 203, 39, 67, 124, 77, 74, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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