Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a02d5d5fdfd2aa14034a57d7a5cbd6ea211a00c4cf14800e81adffb5f39b6ecc

Tx prefix hash: b84d235f09244e13b16fe157476b1812ef34fdaf3f1876f8b773dfe12563d585
Tx public key: 677e4397480550832daf8f45d5ddf4614685df58bcbb014396d4a56bd1a1bfca
Timestamp: 1704556900 Timestamp [UCT]: 2024-01-06 16:01:40 Age [y:d:h:m:s]: 01:350:03:06:45
Block: 929508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509126 RingCT/type: yes/0
Extra: 01677e4397480550832daf8f45d5ddf4614685df58bcbb014396d4a56bd1a1bfca0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc265fefda3d7a085995b6176b1078f642f7deec2e71f4efaa6ab2d65e5ab2b3 0.600000000000 1387384 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": 929518, "vin": [ { "gen": { "height": 929508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc265fefda3d7a085995b6176b1078f642f7deec2e71f4efaa6ab2d65e5ab2b3" } } ], "extra": [ 1, 103, 126, 67, 151, 72, 5, 80, 131, 45, 175, 143, 69, 213, 221, 244, 97, 70, 133, 223, 88, 188, 187, 1, 67, 150, 212, 165, 107, 209, 161, 191, 202, 2, 17, 0, 0, 0, 3, 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