Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f7426df27a5ef5762718797d39dacbca48b92fa041a4240c92248cd8127a646

Tx prefix hash: 3941cccf37aa2c0e01ef978f503661e8547cb1e9a3fe7959a7970dd70410e39e
Tx public key: bc63320f388914c3c92675a6092e7b83e71e5c1d06b3b124da7f9e08a72208dc
Timestamp: 1717613180 Timestamp [UCT]: 2024-06-05 18:46:20 Age [y:d:h:m:s]: 00:230:12:01:27
Block: 1037757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164922 RingCT/type: yes/0
Extra: 01bc63320f388914c3c92675a6092e7b83e71e5c1d06b3b124da7f9e08a72208dc02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce5d48b3406ade1acd6e42adb942b5576da879b33b9c75839901d84e871333ec 0.600000000000 1506312 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": 1037767, "vin": [ { "gen": { "height": 1037757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce5d48b3406ade1acd6e42adb942b5576da879b33b9c75839901d84e871333ec" } } ], "extra": [ 1, 188, 99, 50, 15, 56, 137, 20, 195, 201, 38, 117, 166, 9, 46, 123, 131, 231, 30, 92, 29, 6, 179, 177, 36, 218, 127, 158, 8, 167, 34, 8, 220, 2, 17, 0, 0, 0, 4, 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