Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f22b4754ca44fe2c0b254c2f02b28e872a7b99cf39113e3749c6b8dbac3449b

Tx prefix hash: 9ef6a377c9363705d3d1a0167d5e8d911b7b93ee40f35627e6f74371e552d420
Tx public key: 938824bf3f42afe570ab36d8efc238e593271996282ab568844b993f94a96a19
Timestamp: 1735118863 Timestamp [UCT]: 2024-12-25 09:27:43 Age [y:d:h:m:s]: 00:097:15:47:11
Block: 1182783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69567 RingCT/type: yes/0
Extra: 01938824bf3f42afe570ab36d8efc238e593271996282ab568844b993f94a96a190211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd31aea8a3364fd7ef24e7583b23fc9cdfe45a0355e1e5d59d9ee9be11d9c52a 0.600000000000 1669222 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": 1182793, "vin": [ { "gen": { "height": 1182783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd31aea8a3364fd7ef24e7583b23fc9cdfe45a0355e1e5d59d9ee9be11d9c52a" } } ], "extra": [ 1, 147, 136, 36, 191, 63, 66, 175, 229, 112, 171, 54, 216, 239, 194, 56, 229, 147, 39, 25, 150, 40, 42, 181, 104, 132, 75, 153, 63, 148, 169, 106, 25, 2, 17, 0, 0, 0, 8, 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