Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bc513446ed199e4608a73120e6c57f1df8e0f5b6e1d7d1a11939ef3c0b04635

Tx prefix hash: b7362ad42d018e1b3e6c2af4d536d839ef5a7d1ab851a963b97395a15514c26c
Tx public key: 69d68d56d8fa4573801d07776c7e6260d1eca60561feb330a2a94477b3176ef6
Timestamp: 1580795539 Timestamp [UCT]: 2020-02-04 05:52:19 Age [y:d:h:m:s]: 04:295:16:49:15
Block: 58450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102542 RingCT/type: yes/0
Extra: 0169d68d56d8fa4573801d07776c7e6260d1eca60561feb330a2a94477b3176ef602110000000d4ac5aa02000000000000000000

1 output(s) for total of 392.951735583000 dcy

stealth address amount amount idx
00: 4a940ced48197ceb1bf81048eee6e6697c83763858cf7d24aa5175ac0d46a639 392.951735583000 107966 of 0

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": 58460, "vin": [ { "gen": { "height": 58450 } } ], "vout": [ { "amount": 392951735583, "target": { "key": "4a940ced48197ceb1bf81048eee6e6697c83763858cf7d24aa5175ac0d46a639" } } ], "extra": [ 1, 105, 214, 141, 86, 216, 250, 69, 115, 128, 29, 7, 119, 108, 126, 98, 96, 209, 236, 166, 5, 97, 254, 179, 48, 162, 169, 68, 119, 179, 23, 110, 246, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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