Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e20a6c8c8ceddd3841ab1e6ceb5982bd5db156e17869e237f29aefb3089ef6a

Tx prefix hash: 0c9587a59b19a91259ba3c91b6a0e5c9b7810f7c88791d0c874789694cac6e26
Tx public key: 16170afb288787c39dff4f1a8bf24d7e3ed9cd50d95de9f4a9182524480cbcb3
Timestamp: 1659358101 Timestamp [UCT]: 2022-08-01 12:48:21 Age [y:d:h:m:s]: 02:320:23:37:06
Block: 556397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 750557 RingCT/type: yes/0
Extra: 0116170afb288787c39dff4f1a8bf24d7e3ed9cd50d95de9f4a9182524480cbcb30211000000096570b1ef000000000000000000

1 output(s) for total of 8.798849523000 dcy

stealth address amount amount idx
00: b09d9f7fc0096efee944e0dc35d57ec202e2a189b43bdb74356ed95878fc3966 8.798849523000 988335 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": 556407, "vin": [ { "gen": { "height": 556397 } } ], "vout": [ { "amount": 8798849523, "target": { "key": "b09d9f7fc0096efee944e0dc35d57ec202e2a189b43bdb74356ed95878fc3966" } } ], "extra": [ 1, 22, 23, 10, 251, 40, 135, 135, 195, 157, 255, 79, 26, 139, 242, 77, 126, 62, 217, 205, 80, 217, 93, 233, 244, 169, 24, 37, 36, 72, 12, 188, 179, 2, 17, 0, 0, 0, 9, 101, 112, 177, 239, 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