Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47fc5e4223c009d2a2aac7d3e503b5014524e903b1465a19345c7b86ab91f13d

Tx prefix hash: b7f1bbb074778b3ba1d3989809c17bb7b00620a118c25aba5a17369071ac7dd8
Tx public key: 5406b57c2a3e7592856006dcc077f9f863f70aae26ab7efa5fbf1efc2eb202cf
Timestamp: 1703658274 Timestamp [UCT]: 2023-12-27 06:24:34 Age [y:d:h:m:s]: 01:101:06:46:27
Block: 922073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333492 RingCT/type: yes/0
Extra: 015406b57c2a3e7592856006dcc077f9f863f70aae26ab7efa5fbf1efc2eb202cf021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cce3562974dd4ecd1a641bb684a149c1a287fc9b0a9b6fe7402b6cb94a2c8cd 0.600000000000 1379767 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": 922083, "vin": [ { "gen": { "height": 922073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cce3562974dd4ecd1a641bb684a149c1a287fc9b0a9b6fe7402b6cb94a2c8cd" } } ], "extra": [ 1, 84, 6, 181, 124, 42, 62, 117, 146, 133, 96, 6, 220, 192, 119, 249, 248, 99, 247, 10, 174, 38, 171, 126, 250, 95, 191, 30, 252, 46, 178, 2, 207, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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