Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa55fad591e62a8b711679dc0084c3c1c2d182fc7175bdd9764380c12897734a

Tx prefix hash: 0853ece2c9c5000cd85315a4b70c8163b94ad708178e39dc59e7beec86c94655
Tx public key: 1c067361e748422e12c7fd74a7727a20f2c2d5ffe72882397613c16f4fb683a7
Timestamp: 1716777567 Timestamp [UCT]: 2024-05-27 02:39:27 Age [y:d:h:m:s]: 00:230:08:06:30
Block: 1030842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164850 RingCT/type: yes/0
Extra: 011c067361e748422e12c7fd74a7727a20f2c2d5ffe72882397613c16f4fb683a702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83c8f473093b1eba5c8efc294d4d79122f08d24a1999d21209f9c38241937d8e 0.600000000000 1499147 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": 1030852, "vin": [ { "gen": { "height": 1030842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83c8f473093b1eba5c8efc294d4d79122f08d24a1999d21209f9c38241937d8e" } } ], "extra": [ 1, 28, 6, 115, 97, 231, 72, 66, 46, 18, 199, 253, 116, 167, 114, 122, 32, 242, 194, 213, 255, 231, 40, 130, 57, 118, 19, 193, 111, 79, 182, 131, 167, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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