Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f77eef0ef97d119e814c51791934a082cbe5a42e61fc74ece1ae37e15603488a

Tx prefix hash: c655428f43bf3db3efd5c76d5170ca1c5f28ebe6bd252337ea223b2b00a42a79
Tx public key: 38d174d97fd28631eba18bc5de54e1a14de068b3b21f554a359bff7683f8fcde
Timestamp: 1704325677 Timestamp [UCT]: 2024-01-03 23:47:57 Age [y:d:h:m:s]: 01:112:13:32:33
Block: 927613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341555 RingCT/type: yes/0
Extra: 0138d174d97fd28631eba18bc5de54e1a14de068b3b21f554a359bff7683f8fcde021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8d3e9f29ee83d3f2a61ebf86279dab1b1ce4982d511fb2ad54606d9edae6389 0.600000000000 1385449 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": 927623, "vin": [ { "gen": { "height": 927613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8d3e9f29ee83d3f2a61ebf86279dab1b1ce4982d511fb2ad54606d9edae6389" } } ], "extra": [ 1, 56, 209, 116, 217, 127, 210, 134, 49, 235, 161, 139, 197, 222, 84, 225, 161, 77, 224, 104, 179, 178, 31, 85, 74, 53, 155, 255, 118, 131, 248, 252, 222, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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