Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48e379339096bd83f901f9509e86ce9d3a6d9b77eec9a178cd0b5af815af22e9

Tx prefix hash: 21b1203762afea02d4973300870de949f84084dc3bc9e9ad422bc074e2a04ae5
Tx public key: bf9817eee5dad63f1dc2680c9a8a93847f64a344be01374886c55dcb334e4f34
Timestamp: 1725894433 Timestamp [UCT]: 2024-09-09 15:07:13 Age [y:d:h:m:s]: 00:197:19:06:50
Block: 1106427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141180 RingCT/type: yes/0
Extra: 01bf9817eee5dad63f1dc2680c9a8a93847f64a344be01374886c55dcb334e4f34021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51838c7ed229254618dadad9eea722b5a4ebfdc419bf1e956b7a4fc7e26c1df7 0.600000000000 1584026 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": 1106437, "vin": [ { "gen": { "height": 1106427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51838c7ed229254618dadad9eea722b5a4ebfdc419bf1e956b7a4fc7e26c1df7" } } ], "extra": [ 1, 191, 152, 23, 238, 229, 218, 214, 63, 29, 194, 104, 12, 154, 138, 147, 132, 127, 100, 163, 68, 190, 1, 55, 72, 134, 197, 93, 203, 51, 78, 79, 52, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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