Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 606ab9821b5c6bcf8c764ee1f506d6d7686c82386697b5995782d7f26059bf3f

Tx prefix hash: 3c39e5c66caf6e63f3433be498a81c278c34dfb5af2b5661b32c07c24d4a01c2
Tx public key: 4eecbd873e8110507ed4bef51c1d43f931050fa82c21cda77d8c439646f9e4e4
Timestamp: 1713657003 Timestamp [UCT]: 2024-04-20 23:50:03 Age [y:d:h:m:s]: 00:204:05:41:10
Block: 1004958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146209 RingCT/type: yes/0
Extra: 014eecbd873e8110507ed4bef51c1d43f931050fa82c21cda77d8c439646f9e4e40211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b0e87ebf40cf8762c20113bb9960d1b6861d4e348b92818286a24ab99b3771b 0.600000000000 1465532 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": 1004968, "vin": [ { "gen": { "height": 1004958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b0e87ebf40cf8762c20113bb9960d1b6861d4e348b92818286a24ab99b3771b" } } ], "extra": [ 1, 78, 236, 189, 135, 62, 129, 16, 80, 126, 212, 190, 245, 28, 29, 67, 249, 49, 5, 15, 168, 44, 33, 205, 167, 125, 140, 67, 150, 70, 249, 228, 228, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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