Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f589593818ce1f62c23e88ab95e31171c813d22fe712a52350aa0cd78dd3a0b2

Tx prefix hash: ed5eb251917461bf45486bbdf4132f6156f1e33c12ef20e8ce32ea57870623f7
Tx public key: 6c0b7cf3aa4a38958ccbc60c7d0bf03eb30a0f70da0a08de838a2bc88f7a1ca1
Timestamp: 1711266635 Timestamp [UCT]: 2024-03-24 07:50:35 Age [y:d:h:m:s]: 01:064:21:37:54
Block: 985168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307381 RingCT/type: yes/0
Extra: 016c0b7cf3aa4a38958ccbc60c7d0bf03eb30a0f70da0a08de838a2bc88f7a1ca102110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ac326902dba4f7448574842b0767f053f0957220ed898053e2512706ee7d2b2 0.600000000000 1445375 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": 985178, "vin": [ { "gen": { "height": 985168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ac326902dba4f7448574842b0767f053f0957220ed898053e2512706ee7d2b2" } } ], "extra": [ 1, 108, 11, 124, 243, 170, 74, 56, 149, 140, 203, 198, 12, 125, 11, 240, 62, 179, 10, 15, 112, 218, 10, 8, 222, 131, 138, 43, 200, 143, 122, 28, 161, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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