Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8088711fdfcfdda2e435226efc2e190db7aadaa74f4a75c94f14f4f891557d7b

Tx prefix hash: 4d8c8a294dee86f3f04f7820820b77c6fd1fd177c5f191ed9e68622629861541
Tx public key: 2f81bb2f1171f0bba4b84d334928dfa4ab14a12ba86f69b9dcbfa2b656c5b0fc
Timestamp: 1721794998 Timestamp [UCT]: 2024-07-24 04:23:18 Age [y:d:h:m:s]: 00:308:21:02:06
Block: 1072432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220716 RingCT/type: yes/0
Extra: 012f81bb2f1171f0bba4b84d334928dfa4ab14a12ba86f69b9dcbfa2b656c5b0fc021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a94cda6d535662fb95c83a4fb0ac5e33040f3f6301bbaa2791f918b5b43e0567 0.600000000000 1544901 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": 1072442, "vin": [ { "gen": { "height": 1072432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a94cda6d535662fb95c83a4fb0ac5e33040f3f6301bbaa2791f918b5b43e0567" } } ], "extra": [ 1, 47, 129, 187, 47, 17, 113, 240, 187, 164, 184, 77, 51, 73, 40, 223, 164, 171, 20, 161, 43, 168, 111, 105, 185, 220, 191, 162, 182, 86, 197, 176, 252, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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