Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f338b5ac60d13e041fb8b8a3da91758e0b9a5a5816918101e78d4a0eac867210

Tx prefix hash: 728495c84b11e2e311f51bfe1397babf50295d08d839454bb732620722dda5aa
Tx public key: e8a8e8e9b7e491d36ab8d4e19dba6dbdc10f1912494ebdd55091eebfbb8af49b
Timestamp: 1713666397 Timestamp [UCT]: 2024-04-21 02:26:37 Age [y:d:h:m:s]: 00:350:01:32:50
Block: 1005039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250259 RingCT/type: yes/0
Extra: 01e8a8e8e9b7e491d36ab8d4e19dba6dbdc10f1912494ebdd55091eebfbb8af49b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c128a0a12860df3a43f63f1066690429c7166dab9e823c5f8a47d7aebfb96958 0.600000000000 1465617 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": 1005049, "vin": [ { "gen": { "height": 1005039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c128a0a12860df3a43f63f1066690429c7166dab9e823c5f8a47d7aebfb96958" } } ], "extra": [ 1, 232, 168, 232, 233, 183, 228, 145, 211, 106, 184, 212, 225, 157, 186, 109, 189, 193, 15, 25, 18, 73, 78, 189, 213, 80, 145, 238, 191, 187, 138, 244, 155, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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