Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ceab80869aaa4edef92b3f39d178287b6a42ff3fa2346688fd9af61f852505c9

Tx prefix hash: c1beed856562bb4a6daa9d25a2b21241ba8765c788be0b27813b7606ba123d91
Tx public key: baf3fef1e18cc09af898cbc5f9d9e8941b1eab49ae44aaba0e2033da7860c590
Timestamp: 1718265373 Timestamp [UCT]: 2024-06-13 07:56:13 Age [y:d:h:m:s]: 00:327:16:43:17
Block: 1043179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234200 RingCT/type: yes/0
Extra: 01baf3fef1e18cc09af898cbc5f9d9e8941b1eab49ae44aaba0e2033da7860c5900211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08cc6cbf937e35e0ef166ea4b4b929061c6d16e14edb5aa5fb6a2699c3b547b7 0.600000000000 1512272 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": 1043189, "vin": [ { "gen": { "height": 1043179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08cc6cbf937e35e0ef166ea4b4b929061c6d16e14edb5aa5fb6a2699c3b547b7" } } ], "extra": [ 1, 186, 243, 254, 241, 225, 140, 192, 154, 248, 152, 203, 197, 249, 217, 232, 148, 27, 30, 171, 73, 174, 68, 170, 186, 14, 32, 51, 218, 120, 96, 197, 144, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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