Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34268ae7ee9802f6e021dc6f78e93cc13326408b3dc91ffa5073e8a1cdfd6556

Tx prefix hash: ec57e201f8ee807fb0cded93bbbbcc2ee65e6e1611b56f2fd82c86d4c73a2416
Tx public key: 5f9e4339d0a09835fa48a3bf5847f6bfadef8a496fe7789e47060412bdce85e1
Timestamp: 1727599866 Timestamp [UCT]: 2024-09-29 08:51:06 Age [y:d:h:m:s]: 00:023:19:34:35
Block: 1120568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17023 RingCT/type: yes/0
Extra: 015f9e4339d0a09835fa48a3bf5847f6bfadef8a496fe7789e47060412bdce85e102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d9f7f9c7619e368abaf5f3f9b6dd0e1718eed7e74c33405d2c27eba6e5268c4 0.600000000000 1602527 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": 1120578, "vin": [ { "gen": { "height": 1120568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d9f7f9c7619e368abaf5f3f9b6dd0e1718eed7e74c33405d2c27eba6e5268c4" } } ], "extra": [ 1, 95, 158, 67, 57, 208, 160, 152, 53, 250, 72, 163, 191, 88, 71, 246, 191, 173, 239, 138, 73, 111, 231, 120, 158, 71, 6, 4, 18, 189, 206, 133, 225, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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