Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e877ef0fb5dbdd4e2d58b813430c11981037205b50cd2f6603461c264087eff1

Tx prefix hash: 55196ad2fc1f131f8cd02ff4f8b3a3b99beab635c8c8ded4e2826d0e416e4f8e
Tx public key: 04660734989b499cf9b1766f29efae021bb541c3a7d7eb7db9f2ab996343ac8f
Timestamp: 1721007928 Timestamp [UCT]: 2024-07-15 01:45:28 Age [y:d:h:m:s]: 00:132:08:59:49
Block: 1065925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94704 RingCT/type: yes/0
Extra: 0104660734989b499cf9b1766f29efae021bb541c3a7d7eb7db9f2ab996343ac8f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 230a6507d326149216b3ccae5ee4f94baf4291c9c70fad8559a1d7608701a350 0.600000000000 1536494 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": 1065935, "vin": [ { "gen": { "height": 1065925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "230a6507d326149216b3ccae5ee4f94baf4291c9c70fad8559a1d7608701a350" } } ], "extra": [ 1, 4, 102, 7, 52, 152, 155, 73, 156, 249, 177, 118, 111, 41, 239, 174, 2, 27, 181, 65, 195, 167, 215, 235, 125, 185, 242, 171, 153, 99, 67, 172, 143, 2, 17, 0, 0, 0, 2, 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