Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb55e0ff3211cbe10715435b851fcb0f0c3b960bf078a322c0a7d07e53ca422b

Tx prefix hash: 694338ce6a0c6c4e8121cc766f6212abd53ac44c7dc9949cf5fc8c1adba4dd81
Tx public key: b24f18be0cbee8b76dfc9260a7be0c1120313ca8b1a6ae519db12c34afc78abc
Timestamp: 1705146387 Timestamp [UCT]: 2024-01-13 11:46:27 Age [y:d:h:m:s]: 01:305:16:59:31
Block: 934395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477317 RingCT/type: yes/0
Extra: 01b24f18be0cbee8b76dfc9260a7be0c1120313ca8b1a6ae519db12c34afc78abc02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4b72bdd03fbb80cd76b6c4647e9ea0774b5d30dfc13a76ac12f6ac88d80b105 0.600000000000 1392403 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": 934405, "vin": [ { "gen": { "height": 934395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4b72bdd03fbb80cd76b6c4647e9ea0774b5d30dfc13a76ac12f6ac88d80b105" } } ], "extra": [ 1, 178, 79, 24, 190, 12, 190, 232, 183, 109, 252, 146, 96, 167, 190, 12, 17, 32, 49, 60, 168, 177, 166, 174, 81, 157, 177, 44, 52, 175, 199, 138, 188, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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