Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fbfae166fa9c24060365c61c167f6eec5ed39bfc314c0d000a63ceddd2319b1

Tx prefix hash: b49496ad666af08a179b1aac4dcd7e863be28e6d0ba935f26d3bb6cac89b45d9
Tx public key: f86667b4a3df5e451a86005ce840d1c7c825fb9101dfa97de9b13e319097633e
Timestamp: 1734167088 Timestamp [UCT]: 2024-12-14 09:04:48 Age [y:d:h:m:s]: 00:117:01:51:49
Block: 1174913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83457 RingCT/type: yes/0
Extra: 01f86667b4a3df5e451a86005ce840d1c7c825fb9101dfa97de9b13e319097633e0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6c8fc92618505adfa6d74e40dbdd8681f147365eedc94c9046c52c7d84ae13e 0.600000000000 1661124 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": 1174923, "vin": [ { "gen": { "height": 1174913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6c8fc92618505adfa6d74e40dbdd8681f147365eedc94c9046c52c7d84ae13e" } } ], "extra": [ 1, 248, 102, 103, 180, 163, 223, 94, 69, 26, 134, 0, 92, 232, 64, 209, 199, 200, 37, 251, 145, 1, 223, 169, 125, 233, 177, 62, 49, 144, 151, 99, 62, 2, 17, 0, 0, 0, 9, 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