Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44b616f9e68f6294b7d865cc5dc844c3c391d01f7e249e7676cff371a21c071e

Tx prefix hash: 339b2b53c7a77b52a9308935608203464b615870d56e29b4dac9e0005457edd9
Tx public key: bc6ebcc50318c06d19c4ff604e8807822152c9f1446847bb83959f1689e546b5
Timestamp: 1616842628 Timestamp [UCT]: 2021-03-27 10:57:08 Age [y:d:h:m:s]: 03:273:03:00:26
Block: 227532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 954675 RingCT/type: yes/0
Extra: 01bc6ebcc50318c06d19c4ff604e8807822152c9f1446847bb83959f1689e546b502110000008aa9e81d35000000000000000000

1 output(s) for total of 108.166459888000 dcy

stealth address amount amount idx
00: 026ca89c3024e7bc7c60491e3e8c4f65e2b76e2ad2fde362bcf893834089f788 108.166459888000 471670 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": 227542, "vin": [ { "gen": { "height": 227532 } } ], "vout": [ { "amount": 108166459888, "target": { "key": "026ca89c3024e7bc7c60491e3e8c4f65e2b76e2ad2fde362bcf893834089f788" } } ], "extra": [ 1, 188, 110, 188, 197, 3, 24, 192, 109, 25, 196, 255, 96, 78, 136, 7, 130, 33, 82, 201, 241, 68, 104, 71, 187, 131, 149, 159, 22, 137, 229, 70, 181, 2, 17, 0, 0, 0, 138, 169, 232, 29, 53, 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