Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a34777fe25b356e5df4a3adf8491bdf8877d4a5638e3645b27d764023f8bd461

Tx prefix hash: 33d1ba4845e64d8b3a9332a957980297b958f4968d802cff061f02bc7b2532be
Tx public key: bf31f0d9b2cac7f8800d2cc0c667c4f2a5d9db0cebb01a3e34da8b9883ee59e5
Timestamp: 1575875883 Timestamp [UCT]: 2019-12-09 07:18:03 Age [y:d:h:m:s]: 05:062:18:06:33
Block: 23755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190706 RingCT/type: yes/0
Extra: 01bf31f0d9b2cac7f8800d2cc0c667c4f2a5d9db0cebb01a3e34da8b9883ee59e5021100000013ad433a0b000000000000000000

1 output(s) for total of 512.024444726000 dcy

stealth address amount amount idx
00: 60ec4105119033ecbda2e7fbf03c9eb518315c6be041c9366d3a1c77de6ae6c4 512.024444726000 38496 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": 23765, "vin": [ { "gen": { "height": 23755 } } ], "vout": [ { "amount": 512024444726, "target": { "key": "60ec4105119033ecbda2e7fbf03c9eb518315c6be041c9366d3a1c77de6ae6c4" } } ], "extra": [ 1, 191, 49, 240, 217, 178, 202, 199, 248, 128, 13, 44, 192, 198, 103, 196, 242, 165, 217, 219, 12, 235, 176, 26, 62, 52, 218, 139, 152, 131, 238, 89, 229, 2, 17, 0, 0, 0, 19, 173, 67, 58, 11, 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