Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6b8d50c702cbc1e1e2176167c81d170328f748df0894174e8e113486b0c4707

Tx prefix hash: 07627e1fefc3b4f120958c83f2f526ccf51cd07b774e58cd203cc64626f62ba3
Tx public key: 9f3a89d41589d2e5585b14b11d3cfc73d76956eedab650dcc52de93a96d62b64
Timestamp: 1577700776 Timestamp [UCT]: 2019-12-30 10:12:56 Age [y:d:h:m:s]: 05:042:17:06:16
Block: 34927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1180307 RingCT/type: yes/0
Extra: 019f3a89d41589d2e5585b14b11d3cfc73d76956eedab650dcc52de93a96d62b640211000000078a2ee0d9000000000000000000

1 output(s) for total of 470.189801729000 dcy

stealth address amount amount idx
00: 6542fcad08a8af38bf4cde501ebd9994245b4f8132d407b42c18ff0cf38b2d5c 470.189801729000 58844 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": 34937, "vin": [ { "gen": { "height": 34927 } } ], "vout": [ { "amount": 470189801729, "target": { "key": "6542fcad08a8af38bf4cde501ebd9994245b4f8132d407b42c18ff0cf38b2d5c" } } ], "extra": [ 1, 159, 58, 137, 212, 21, 137, 210, 229, 88, 91, 20, 177, 29, 60, 252, 115, 215, 105, 86, 238, 218, 182, 80, 220, 197, 45, 233, 58, 150, 214, 43, 100, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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