Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a61ef63bb21e7d64e274f525c475a8d831cc77332da739efee53d4d9d214c8e3

Tx prefix hash: 243d342b49c535645a11b346eca1d5329229c3aece662d08d85e5e141c5a1a00
Tx public key: 1ae93c31571028bfcf703034ca7eb6d41a58acc1624259538db6eff96933aa5c
Timestamp: 1673872327 Timestamp [UCT]: 2023-01-16 12:32:07 Age [y:d:h:m:s]: 02:002:10:54:18
Block: 675991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523648 RingCT/type: yes/0
Extra: 011ae93c31571028bfcf703034ca7eb6d41a58acc1624259538db6eff96933aa5c0211000000048b7b6602000000000000000000

1 output(s) for total of 3.533142454000 dcy

stealth address amount amount idx
00: 8f54db0cc5f2c3013250c14866f69f9a3c0af97ef08d7bbb7f766e8c4e209db3 3.533142454000 1117686 of 0

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": 676001, "vin": [ { "gen": { "height": 675991 } } ], "vout": [ { "amount": 3533142454, "target": { "key": "8f54db0cc5f2c3013250c14866f69f9a3c0af97ef08d7bbb7f766e8c4e209db3" } } ], "extra": [ 1, 26, 233, 60, 49, 87, 16, 40, 191, 207, 112, 48, 52, 202, 126, 182, 212, 26, 88, 172, 193, 98, 66, 89, 83, 141, 182, 239, 249, 105, 51, 170, 92, 2, 17, 0, 0, 0, 4, 139, 123, 102, 2, 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