Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31279e506f87f89b81c5b7cb27fe0aa445b65714bffa6394348317cb857aff52

Tx prefix hash: 865569e5afa2f83cbb2630bc8f3885d8ea542ecddf9242cf11127b514898e391
Tx public key: 8da638843a912131971f354e4b32ff5c48d4f035a94b6c95b1d0a77479c477df
Timestamp: 1739053730 Timestamp [UCT]: 2025-02-08 22:28:50 Age [y:d:h:m:s]: 00:333:20:00:22
Block: 1215090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236419 RingCT/type: yes/0
Extra: 018da638843a912131971f354e4b32ff5c48d4f035a94b6c95b1d0a77479c477df021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b959282358c9bc9316541681f4e6edcf77c4fd1f8392a2d3463ba9731fe90e 0.600000000000 1701887 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": 1215100, "vin": [ { "gen": { "height": 1215090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b959282358c9bc9316541681f4e6edcf77c4fd1f8392a2d3463ba9731fe90e" } } ], "extra": [ 1, 141, 166, 56, 132, 58, 145, 33, 49, 151, 31, 53, 78, 75, 50, 255, 92, 72, 212, 240, 53, 169, 75, 108, 149, 177, 208, 167, 116, 121, 196, 119, 223, 2, 17, 0, 0, 0, 5, 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