Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfc1d4a41418156c5d3e1d3860f7fec0cea37424134f02b6b4c00bc2820b37c4

Tx prefix hash: f79905fb8c07e4cb11f15af11fe8d0f8ec5e78cdde2d956b6a2ee73d32b9ab50
Tx public key: e5a7c87fc4751db6df9eb20a92425d23b1af81c3e7f57e60addcac542b354566
Timestamp: 1578977137 Timestamp [UCT]: 2020-01-14 04:45:37 Age [y:d:h:m:s]: 05:122:04:49:00
Block: 45133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1237520 RingCT/type: yes/0
Extra: 01e5a7c87fc4751db6df9eb20a92425d23b1af81c3e7f57e60addcac542b35456602111857e66f00000000000000000000000000

1 output(s) for total of 434.967166544000 dcy

stealth address amount amount idx
00: b04415c4b88ea8b65f25bba03cb1ac974cf610c80f04f597e2b7c256d2015765 434.967166544000 82343 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": 45143, "vin": [ { "gen": { "height": 45133 } } ], "vout": [ { "amount": 434967166544, "target": { "key": "b04415c4b88ea8b65f25bba03cb1ac974cf610c80f04f597e2b7c256d2015765" } } ], "extra": [ 1, 229, 167, 200, 127, 196, 117, 29, 182, 223, 158, 178, 10, 146, 66, 93, 35, 177, 175, 129, 195, 231, 245, 126, 96, 173, 220, 172, 84, 43, 53, 69, 102, 2, 17, 24, 87, 230, 111, 0, 0, 0, 0, 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