Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b3db17d7c3a3a523115d5d6172187ecb43bdaa2767502a1f0b0142006c8745f

Tx prefix hash: 7dd8ce90c3291d5cbdaaba5aef22301728d627978c89dd88c69f86bd00de4d8f
Tx public key: f8b1d378b4e7bb0fc54784e9eb7fcafee9c681b5da495330c7cf7c25316250a2
Timestamp: 1657112480 Timestamp [UCT]: 2022-07-06 13:01:20 Age [y:d:h:m:s]: 02:303:14:17:27
Block: 537889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 738129 RingCT/type: yes/0
Extra: 01f8b1d378b4e7bb0fc54784e9eb7fcafee9c681b5da495330c7cf7c25316250a20211000000014da16a3a000000000000000000

1 output(s) for total of 10.133293102000 dcy

stealth address amount amount idx
00: c2cc532bd7658abd1e5c9eab042e8b6d4c3fc3e0d83321dc04f01e816d3c6dc6 10.133293102000 967824 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": 537899, "vin": [ { "gen": { "height": 537889 } } ], "vout": [ { "amount": 10133293102, "target": { "key": "c2cc532bd7658abd1e5c9eab042e8b6d4c3fc3e0d83321dc04f01e816d3c6dc6" } } ], "extra": [ 1, 248, 177, 211, 120, 180, 231, 187, 15, 197, 71, 132, 233, 235, 127, 202, 254, 233, 198, 129, 181, 218, 73, 83, 48, 199, 207, 124, 37, 49, 98, 80, 162, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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