Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0adf4ab002d31ee5b0dfb5d6d044674018955bfc15c35c476d95d417cf5bda6

Tx prefix hash: cfdb2f5bf835faf15b0caf52b12a13bfdbdfdddea63c5bf35f47b0868244da32
Tx public key: 2a44582f84210cf9dff3e55975f585e83a2386759d5ff155e0422221484e9123
Timestamp: 1578541347 Timestamp [UCT]: 2020-01-09 03:42:27 Age [y:d:h:m:s]: 05:297:11:01:24
Block: 41746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1360248 RingCT/type: yes/0
Extra: 012a44582f84210cf9dff3e55975f585e83a2386759d5ff155e0422221484e91230211000000074ac5aa02000000000000000000

1 output(s) for total of 446.353574947000 dcy

stealth address amount amount idx
00: d3814d0a2cbd090f4f4e1d9b481cf0a839a742006ce9ef71f69575c271f560ef 446.353574947000 74704 of 0

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": 41756, "vin": [ { "gen": { "height": 41746 } } ], "vout": [ { "amount": 446353574947, "target": { "key": "d3814d0a2cbd090f4f4e1d9b481cf0a839a742006ce9ef71f69575c271f560ef" } } ], "extra": [ 1, 42, 68, 88, 47, 132, 33, 12, 249, 223, 243, 229, 89, 117, 245, 133, 232, 58, 35, 134, 117, 157, 95, 241, 85, 224, 66, 34, 33, 72, 78, 145, 35, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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