Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29763b414988c59ca8e4a3ed5f6db4c75e8b053358df89d8302676decff928a0

Tx prefix hash: 5cd7e469d0c2f6f437175932dc95267e323f8acc82ae3889c5faadabbd89b537
Tx public key: 94d663752028c5243280b67ed45e2403a7ee916cc55c4a2a84a399d89deebe5f
Timestamp: 1582101698 Timestamp [UCT]: 2020-02-19 08:41:38 Age [y:d:h:m:s]: 04:281:11:47:44
Block: 68047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093589 RingCT/type: yes/0
Extra: 0194d663752028c5243280b67ed45e2403a7ee916cc55c4a2a84a399d89deebe5f0211000000017adf42d3000000000000000000

1 output(s) for total of 365.201748265000 dcy

stealth address amount amount idx
00: 335fdbe8cbe015a20b3b245c3286ec0fae69edf40a8962a8848c524fa716daaa 365.201748265000 125339 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": 68057, "vin": [ { "gen": { "height": 68047 } } ], "vout": [ { "amount": 365201748265, "target": { "key": "335fdbe8cbe015a20b3b245c3286ec0fae69edf40a8962a8848c524fa716daaa" } } ], "extra": [ 1, 148, 214, 99, 117, 32, 40, 197, 36, 50, 128, 182, 126, 212, 94, 36, 3, 167, 238, 145, 108, 197, 92, 74, 42, 132, 163, 153, 216, 157, 238, 190, 95, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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