Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9de4f5cf2aa12290ee18f9d8e0132f024b78896601a87e82cd0e1f19fc875bf1

Tx prefix hash: 27945ce10a30078f590fd45500331183c6febd702512696221aa65c5ef403dbd
Tx public key: f362091dce0f3ff64c989c39e7d52e4aa776537c3cd87379ff7f86f5e8cdc5ef
Timestamp: 1728088180 Timestamp [UCT]: 2024-10-05 00:29:40 Age [y:d:h:m:s]: 01:040:08:49:16
Block: 1124605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287246 RingCT/type: yes/0
Extra: 01f362091dce0f3ff64c989c39e7d52e4aa776537c3cd87379ff7f86f5e8cdc5ef02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 265e80248f60703d1db16569ea0e37a14cd5ec84eafaeac6bbbf5844562e0cf7 0.600000000000 1607254 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": 1124615, "vin": [ { "gen": { "height": 1124605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "265e80248f60703d1db16569ea0e37a14cd5ec84eafaeac6bbbf5844562e0cf7" } } ], "extra": [ 1, 243, 98, 9, 29, 206, 15, 63, 246, 76, 152, 156, 57, 231, 213, 46, 74, 167, 118, 83, 124, 60, 216, 115, 121, 255, 127, 134, 245, 232, 205, 197, 239, 2, 17, 0, 0, 0, 2, 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