Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29817404ddd7fc541e70d791d11da53d37e52101781c93476ffc1518b8af4828

Tx prefix hash: 37abf7ad465e8dd99c9d73c887b7d10a8d2159ceb0a5caaf41c9dcda7b4766c2
Tx public key: d582fe19d75521c52db03be68045314d9c2f3135f30f67fa677f3d4dcef0c41e
Timestamp: 1725152931 Timestamp [UCT]: 2024-09-01 01:08:51 Age [y:d:h:m:s]: 00:214:20:07:34
Block: 1100272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153392 RingCT/type: yes/0
Extra: 01d582fe19d75521c52db03be68045314d9c2f3135f30f67fa677f3d4dcef0c41e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eb45dbdc595ee691d99870777b38fd59dc94ba79d036e07b91f4f09424e1383 0.600000000000 1576247 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": 1100282, "vin": [ { "gen": { "height": 1100272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eb45dbdc595ee691d99870777b38fd59dc94ba79d036e07b91f4f09424e1383" } } ], "extra": [ 1, 213, 130, 254, 25, 215, 85, 33, 197, 45, 176, 59, 230, 128, 69, 49, 77, 156, 47, 49, 53, 243, 15, 103, 250, 103, 127, 61, 77, 206, 240, 196, 30, 2, 17, 0, 0, 0, 4, 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