Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3061f5831f0d912ed052d012f78a4c8f834dde719598a4ccf655f1d1783daf47

Tx prefix hash: 0528f941e6c2f2926f5709f0817e10f60274b8528b448e3ba758696e276d217e
Tx public key: c1baa3394aeceb90a22fdbacc57a1fa0f81cbfc1a931dd2cf14ddd6c20009760
Timestamp: 1719946632 Timestamp [UCT]: 2024-07-02 18:57:12 Age [y:d:h:m:s]: 00:275:07:02:02
Block: 1057114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196688 RingCT/type: yes/0
Extra: 01c1baa3394aeceb90a22fdbacc57a1fa0f81cbfc1a931dd2cf14ddd6c2000976002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 795e796d0cc63bfcda3de6a8a3a3f2e56c6964b74ed0f80d4b1ed52cd7982f1e 0.600000000000 1527543 of 15

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": 1057124, "vin": [ { "gen": { "height": 1057114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "795e796d0cc63bfcda3de6a8a3a3f2e56c6964b74ed0f80d4b1ed52cd7982f1e" } } ], "extra": [ 1, 193, 186, 163, 57, 74, 236, 235, 144, 162, 47, 219, 172, 197, 122, 31, 160, 248, 28, 191, 193, 169, 49, 221, 44, 241, 77, 221, 108, 32, 0, 151, 96, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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