Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f3df09cb1e028683b0c330a52b79d6e6c47f951d1a8490a28085e131cab58c

Tx prefix hash: 8d351e6d6837b09d341969b520e6049c8bde6e138f17b9db559fc8b8468a4bd4
Tx public key: 691c9e10b9ed20e5d94ffb9f12ca18f55a7a851c007786f05ebd00f0b872a98e
Timestamp: 1730765624 Timestamp [UCT]: 2024-11-05 00:13:44 Age [y:d:h:m:s]: 01:010:07:29:30
Block: 1146713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265801 RingCT/type: yes/0
Extra: 01691c9e10b9ed20e5d94ffb9f12ca18f55a7a851c007786f05ebd00f0b872a98e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27a40acbf6a1cc645ab0873a6f7717f5b593c44941810a6943c2bf5d468d177f 0.600000000000 1631404 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": 1146723, "vin": [ { "gen": { "height": 1146713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27a40acbf6a1cc645ab0873a6f7717f5b593c44941810a6943c2bf5d468d177f" } } ], "extra": [ 1, 105, 28, 158, 16, 185, 237, 32, 229, 217, 79, 251, 159, 18, 202, 24, 245, 90, 122, 133, 28, 0, 119, 134, 240, 94, 189, 0, 240, 184, 114, 169, 142, 2, 17, 0, 0, 0, 3, 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