Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27163a0ccd8c2a3444dc8720f0b7a2d03269bcaa9fecf664e9ad0801441301b8

Tx prefix hash: db4d9fe3e90946489069d56a671a00def8f0ada60478fcdd339fb1da8e5ee8a4
Tx public key: 8fbc8bb88cb238263d713518bf7d8846aab1d540c175f605db72c6054cc002f8
Timestamp: 1731686997 Timestamp [UCT]: 2024-11-15 16:09:57 Age [y:d:h:m:s]: 00:215:16:18:25
Block: 1154347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153889 RingCT/type: yes/0
Extra: 018fbc8bb88cb238263d713518bf7d8846aab1d540c175f605db72c6054cc002f8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d8f2cd70872a71452d5c18f5ccc00a08d5f8fb3ebd97eed3a2fd570fbe668c3 0.600000000000 1639958 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": 1154357, "vin": [ { "gen": { "height": 1154347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d8f2cd70872a71452d5c18f5ccc00a08d5f8fb3ebd97eed3a2fd570fbe668c3" } } ], "extra": [ 1, 143, 188, 139, 184, 140, 178, 56, 38, 61, 113, 53, 24, 191, 125, 136, 70, 170, 177, 213, 64, 193, 117, 246, 5, 219, 114, 198, 5, 76, 192, 2, 248, 2, 17, 0, 0, 0, 1, 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