Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ee9c1320c79f5be8e9b979a2b790d517e67ecff7d258349f1d496f02c2b869d

Tx prefix hash: 31287a5a069e2b2b79cb209a447433d01cb90543be715b924542d0bfa1f30bd7
Tx public key: 886228da16e3e78a825b5da7d0f03fce4bd814b833033986edbd6aba4bc7cf7e
Timestamp: 1722918256 Timestamp [UCT]: 2024-08-06 04:24:16 Age [y:d:h:m:s]: 00:251:19:05:24
Block: 1081745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179851 RingCT/type: yes/0
Extra: 01886228da16e3e78a825b5da7d0f03fce4bd814b833033986edbd6aba4bc7cf7e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc808fde559100975736f602dc2268035fb5584ace6ceea7f537d09254ac3080 0.600000000000 1555566 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": 1081755, "vin": [ { "gen": { "height": 1081745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc808fde559100975736f602dc2268035fb5584ace6ceea7f537d09254ac3080" } } ], "extra": [ 1, 136, 98, 40, 218, 22, 227, 231, 138, 130, 91, 93, 167, 208, 240, 63, 206, 75, 216, 20, 184, 51, 3, 57, 134, 237, 189, 106, 186, 75, 199, 207, 126, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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