Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f51a3e9936414a387129cbbf8a8cadee2ad75fb03d23b0d2c7ab170a5142494

Tx prefix hash: 432d63f81ea60e356ffed80b9cd521f46bf37686a18c403930dadaabe3790133
Tx public key: 96752cbf9f4d79485c072da78747c9a7ea35b05b28a9d5a8763e0cd4c9a9e31b
Timestamp: 1577894580 Timestamp [UCT]: 2020-01-01 16:03:00 Age [y:d:h:m:s]: 05:007:21:18:26
Block: 36418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155774 RingCT/type: yes/0
Extra: 0196752cbf9f4d79485c072da78747c9a7ea35b05b28a9d5a8763e0cd4c9a9e31b021100000026d81c26c0000000000000000000

1 output(s) for total of 464.871478012000 dcy

stealth address amount amount idx
00: 1f7398c94cf6009fd7e9f51a79da798700805c225c0c9d57a51177eeb4f5f523 464.871478012000 61699 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": 36428, "vin": [ { "gen": { "height": 36418 } } ], "vout": [ { "amount": 464871478012, "target": { "key": "1f7398c94cf6009fd7e9f51a79da798700805c225c0c9d57a51177eeb4f5f523" } } ], "extra": [ 1, 150, 117, 44, 191, 159, 77, 121, 72, 92, 7, 45, 167, 135, 71, 201, 167, 234, 53, 176, 91, 40, 169, 213, 168, 118, 62, 12, 212, 201, 169, 227, 27, 2, 17, 0, 0, 0, 38, 216, 28, 38, 192, 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