Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f69fa1461e3519ab4dd6fcecd9431ced2fa742eaf9804718c25bd3472d0cd7f

Tx prefix hash: 234ca090c172a9a2b7052cb1489d1717cbd1a6a86ab4d720f79762c71dd0d256
Tx public key: 8a21cb1b7ee2a1e9fc85bda34fe266338b00a4a7b5f81a8aa1b2eae94be543df
Timestamp: 1677675600 Timestamp [UCT]: 2023-03-01 13:00:00 Age [y:d:h:m:s]: 01:276:23:00:05
Block: 707545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458855 RingCT/type: yes/0
Extra: 018a21cb1b7ee2a1e9fc85bda34fe266338b00a4a7b5f81a8aa1b2eae94be543df02110000000183600029000000000000000000

1 output(s) for total of 2.777545634000 dcy

stealth address amount amount idx
00: e4d635a08facad2a537729af5593c9dc4eec1aae52a04b0b8dccf387a7d1a044 2.777545634000 1151356 of 0

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": 707555, "vin": [ { "gen": { "height": 707545 } } ], "vout": [ { "amount": 2777545634, "target": { "key": "e4d635a08facad2a537729af5593c9dc4eec1aae52a04b0b8dccf387a7d1a044" } } ], "extra": [ 1, 138, 33, 203, 27, 126, 226, 161, 233, 252, 133, 189, 163, 79, 226, 102, 51, 139, 0, 164, 167, 181, 248, 26, 138, 161, 178, 234, 233, 75, 229, 67, 223, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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