Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dde94bb80573d0bd6a5212f8abf63a83a992b5013e040d8d609b04aa740a8afa

Tx prefix hash: b58cfa5d3c1a9ba475574c444dd8df32b3e5d0e1f355907af3e9df3ee222f18c
Tx public key: 3619e9e584d96118904e52a49ee73ccdd35e42a29ad9aca4ecc99c2bd7aa7238
Timestamp: 1731818558 Timestamp [UCT]: 2024-11-17 04:42:38 Age [y:d:h:m:s]: 00:006:17:54:09
Block: 1155440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4832 RingCT/type: yes/0
Extra: 013619e9e584d96118904e52a49ee73ccdd35e42a29ad9aca4ecc99c2bd7aa7238021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79a8806a8d2a28a9beaf4e2646d28543fcfac1c57a3f629cba285cd7311edc51 0.600000000000 1641055 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": 1155450, "vin": [ { "gen": { "height": 1155440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79a8806a8d2a28a9beaf4e2646d28543fcfac1c57a3f629cba285cd7311edc51" } } ], "extra": [ 1, 54, 25, 233, 229, 132, 217, 97, 24, 144, 78, 82, 164, 158, 231, 60, 205, 211, 94, 66, 162, 154, 217, 172, 164, 236, 201, 156, 43, 215, 170, 114, 56, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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