Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e8fa20f6fca10109ef33d757cae713d534b528589072a7a62c6b76d04742d8b

Tx prefix hash: 330a3180125542a75c882559056fa1b45a531570880d6b8df8b218f3a8456d29
Tx public key: bd9dbb2629edef2d9301d3c7279d6b2bdc871ae828790e091d375236dd514480
Timestamp: 1700451554 Timestamp [UCT]: 2023-11-20 03:39:14 Age [y:d:h:m:s]: 01:131:21:54:58
Block: 895488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355440 RingCT/type: yes/0
Extra: 01bd9dbb2629edef2d9301d3c7279d6b2bdc871ae828790e091d375236dd51448002110000000233af99f4000000000000000000

1 output(s) for total of 0.662028234000 dcy

stealth address amount amount idx
00: 741239c9b52fd23ebf214db6173f8bfc42c3643963736299d7478510ea52af30 0.662028234000 1351725 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": 895498, "vin": [ { "gen": { "height": 895488 } } ], "vout": [ { "amount": 662028234, "target": { "key": "741239c9b52fd23ebf214db6173f8bfc42c3643963736299d7478510ea52af30" } } ], "extra": [ 1, 189, 157, 187, 38, 41, 237, 239, 45, 147, 1, 211, 199, 39, 157, 107, 43, 220, 135, 26, 232, 40, 121, 14, 9, 29, 55, 82, 54, 221, 81, 68, 128, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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