Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0045bd20236948201528c08bcbc12c87396cbe88d2e413154f92be41ebb7e06

Tx prefix hash: 27603efb51e8ddf7f322438f3c1129fd2444fb44f775940cfc6811b1332b3eb7
Tx public key: 8fd9fc5e915533634c64d5209b23640c4120b3cdd6fa6a2a08f1a913d6b1729c
Timestamp: 1728544348 Timestamp [UCT]: 2024-10-10 07:12:28 Age [y:d:h:m:s]: 00:105:09:37:17
Block: 1128392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75305 RingCT/type: yes/0
Extra: 018fd9fc5e915533634c64d5209b23640c4120b3cdd6fa6a2a08f1a913d6b1729c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e641656217cacd8fd64ca608b2c15c78e80ffd31c23e402f6ce1ac92ffd2756 0.600000000000 1611209 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": 1128402, "vin": [ { "gen": { "height": 1128392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e641656217cacd8fd64ca608b2c15c78e80ffd31c23e402f6ce1ac92ffd2756" } } ], "extra": [ 1, 143, 217, 252, 94, 145, 85, 51, 99, 76, 100, 213, 32, 155, 35, 100, 12, 65, 32, 179, 205, 214, 250, 106, 42, 8, 241, 169, 19, 214, 177, 114, 156, 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