Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4133446f7b10ae55e7938ea5f970624231eb7cf713f0d1a59ef74678d596e57

Tx prefix hash: 836cc41bf71f23f2d08389a7cefa81bf5ff1f159acc43ac8758ff37fa4c72efd
Tx public key: 60f52838943c851e47035b2f7c9dfeba531a9b3d47444b677ef1d0af48b711d0
Timestamp: 1709254518 Timestamp [UCT]: 2024-03-01 00:55:18 Age [y:d:h:m:s]: 01:031:00:42:22
Block: 968481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283166 RingCT/type: yes/0
Extra: 0160f52838943c851e47035b2f7c9dfeba531a9b3d47444b677ef1d0af48b711d002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba5bf3803c14c60810bdfe8d5b325da21068a98f18cf803285504b885fd4e1af 0.600000000000 1428296 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": 968491, "vin": [ { "gen": { "height": 968481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba5bf3803c14c60810bdfe8d5b325da21068a98f18cf803285504b885fd4e1af" } } ], "extra": [ 1, 96, 245, 40, 56, 148, 60, 133, 30, 71, 3, 91, 47, 124, 157, 254, 186, 83, 26, 155, 61, 71, 68, 75, 103, 126, 241, 208, 175, 72, 183, 17, 208, 2, 17, 0, 0, 0, 3, 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