Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f1eef1a09940bf9c52ec136ebe46306d750c01f2255b1d65b0b6c2af482f2d6

Tx prefix hash: f92ee6e4d7f19c100d58d6769a272d4fc463b3e452a06f68f2d784d3af49d222
Tx public key: 0b8e9a9387a0e6126fd272f7bc043642a882c484ec71795f875b2af9fe357ae6
Timestamp: 1577922099 Timestamp [UCT]: 2020-01-01 23:41:39 Age [y:d:h:m:s]: 05:001:15:47:47
Block: 36718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151245 RingCT/type: yes/0
Extra: 010b8e9a9387a0e6126fd272f7bc043642a882c484ec71795f875b2af9fe357ae60211000000558a2ee0d9000000000000000000

1 output(s) for total of 463.808684319000 dcy

stealth address amount amount idx
00: 36c144d99492f4ddb6a9dc52f78e54bfda7105b4d9fed11585f83703e41075d7 463.808684319000 62260 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": 36728, "vin": [ { "gen": { "height": 36718 } } ], "vout": [ { "amount": 463808684319, "target": { "key": "36c144d99492f4ddb6a9dc52f78e54bfda7105b4d9fed11585f83703e41075d7" } } ], "extra": [ 1, 11, 142, 154, 147, 135, 160, 230, 18, 111, 210, 114, 247, 188, 4, 54, 66, 168, 130, 196, 132, 236, 113, 121, 95, 135, 91, 42, 249, 254, 53, 122, 230, 2, 17, 0, 0, 0, 85, 138, 46, 224, 217, 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