Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efb083cb77b05c19b781bddd59b50b2e8e5b3dd54fba4ec78719a80acdbfd05b

Tx prefix hash: 4f8d3b7f63b2d1860dfdccac390f21ae9736031c9294afd1b6fee9e796ceb27d
Tx public key: 5cdfc5ab0bd546859f820dc27871c007610ae5fc115442dad2d54134d8d6095b
Timestamp: 1734933238 Timestamp [UCT]: 2024-12-23 05:53:58 Age [y:d:h:m:s]: 00:100:09:35:17
Block: 1181267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71518 RingCT/type: yes/0
Extra: 015cdfc5ab0bd546859f820dc27871c007610ae5fc115442dad2d54134d8d6095b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e771e6e018e81caa253dfa8d68c9d00e67ecd3ba0da5129e1ae06a11ef304ac7 0.600000000000 1667684 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": 1181277, "vin": [ { "gen": { "height": 1181267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e771e6e018e81caa253dfa8d68c9d00e67ecd3ba0da5129e1ae06a11ef304ac7" } } ], "extra": [ 1, 92, 223, 197, 171, 11, 213, 70, 133, 159, 130, 13, 194, 120, 113, 192, 7, 97, 10, 229, 252, 17, 84, 66, 218, 210, 213, 65, 52, 216, 214, 9, 91, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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