Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3e7807a897ec0e309e143ec2ad17e69e219f81aab705aa493fc7ba3952beeb

Tx prefix hash: a90c4d5a684fac2088c460364ac337a6c176cd2e01029600e3f6187b6dcf194c
Tx public key: 8eac14c02b8eb12150524bab4f67bd2fb0297b61d8c54a17f226c81098b235f5
Timestamp: 1733527980 Timestamp [UCT]: 2024-12-06 23:33:00 Age [y:d:h:m:s]: 00:102:22:45:32
Block: 1169601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73397 RingCT/type: yes/0
Extra: 018eac14c02b8eb12150524bab4f67bd2fb0297b61d8c54a17f226c81098b235f5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f173ab1a89ee9dc02fc7df3b6e0209c655c392864e40f6fdbaf6bc519b5dffa8 0.600000000000 1655322 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": 1169611, "vin": [ { "gen": { "height": 1169601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f173ab1a89ee9dc02fc7df3b6e0209c655c392864e40f6fdbaf6bc519b5dffa8" } } ], "extra": [ 1, 142, 172, 20, 192, 43, 142, 177, 33, 80, 82, 75, 171, 79, 103, 189, 47, 176, 41, 123, 97, 216, 197, 74, 23, 242, 38, 200, 16, 152, 178, 53, 245, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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