Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0995e1145807b4ef1b115353fb5b69b49bd94995de796a83b1b29ac025db182a

Tx prefix hash: d26253bef5eb58ccbb113d5ef9551dd6fbd77e70aec19430ff3991ab01e5fad5
Tx public key: fe7d475ff3ae00969b71ddc756f81e40324c1a01725dbd1ae2ff4a35962882cb
Timestamp: 1673818111 Timestamp [UCT]: 2023-01-15 21:28:31 Age [y:d:h:m:s]: 02:134:06:35:05
Block: 675544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 617684 RingCT/type: yes/0
Extra: 01fe7d475ff3ae00969b71ddc756f81e40324c1a01725dbd1ae2ff4a35962882cb021100000002044c7254000000000000000000

1 output(s) for total of 3.545212284000 dcy

stealth address amount amount idx
00: 02130a921e4649dc19ad8f5a91e6b7d3fb71dd10ef7fc91d29321f7f22ab3b25 3.545212284000 1117223 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": 675554, "vin": [ { "gen": { "height": 675544 } } ], "vout": [ { "amount": 3545212284, "target": { "key": "02130a921e4649dc19ad8f5a91e6b7d3fb71dd10ef7fc91d29321f7f22ab3b25" } } ], "extra": [ 1, 254, 125, 71, 95, 243, 174, 0, 150, 155, 113, 221, 199, 86, 248, 30, 64, 50, 76, 26, 1, 114, 93, 189, 26, 226, 255, 74, 53, 150, 40, 130, 203, 2, 17, 0, 0, 0, 2, 4, 76, 114, 84, 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