Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b94af01490bdcdf6dbf9ffca048bacccdf85173e7e1000a7eb770e22d6717887

Tx prefix hash: 670eadb5f4a0257d8830117d096618781ed193ddabe1b63074b7c745bf81fbec
Tx public key: 7d67f99c4e4ac786ca9abd7e4e84a33a1ba54c2cb6b096ec1ce37316114e0384
Timestamp: 1577629121 Timestamp [UCT]: 2019-12-29 14:18:41 Age [y:d:h:m:s]: 05:118:11:15:31
Block: 34386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1234435 RingCT/type: yes/0
Extra: 017d67f99c4e4ac786ca9abd7e4e84a33a1ba54c2cb6b096ec1ce37316114e03840211000000068a2ee0d9000000000000000000

1 output(s) for total of 472.142669376000 dcy

stealth address amount amount idx
00: a3baddded7840810ef0e03988e4819d05404be197fbb556624ae9854fdb80aea 472.142669376000 57864 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": 34396, "vin": [ { "gen": { "height": 34386 } } ], "vout": [ { "amount": 472142669376, "target": { "key": "a3baddded7840810ef0e03988e4819d05404be197fbb556624ae9854fdb80aea" } } ], "extra": [ 1, 125, 103, 249, 156, 78, 74, 199, 134, 202, 154, 189, 126, 78, 132, 163, 58, 27, 165, 76, 44, 182, 176, 150, 236, 28, 227, 115, 22, 17, 78, 3, 132, 2, 17, 0, 0, 0, 6, 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