Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 870bd5ae8daa7efa6fedf1056852010763d4824e8bb4634bdbbc46b20e609b3f

Tx prefix hash: 17fcc57b6b7f7f1f62cf434d8524a38b1480336fba91eed106e23e21a6fa594b
Tx public key: 208fe0bd3b87810b5eaee583538803f837b150c4bd7354942b13f4d0fef2d796
Timestamp: 1699878031 Timestamp [UCT]: 2023-11-13 12:20:31 Age [y:d:h:m:s]: 02:002:12:26:11
Block: 890740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521573 RingCT/type: yes/0
Extra: 01208fe0bd3b87810b5eaee583538803f837b150c4bd7354942b13f4d0fef2d796021100000003faf35c9c000000000000000000

1 output(s) for total of 0.686449532000 dcy

stealth address amount amount idx
00: 1a6f2cf20a332fda2d929f918004c75d8c515d54c46c859f455819114d5b4c69 0.686449532000 1346771 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": 890750, "vin": [ { "gen": { "height": 890740 } } ], "vout": [ { "amount": 686449532, "target": { "key": "1a6f2cf20a332fda2d929f918004c75d8c515d54c46c859f455819114d5b4c69" } } ], "extra": [ 1, 32, 143, 224, 189, 59, 135, 129, 11, 94, 174, 229, 131, 83, 136, 3, 248, 55, 177, 80, 196, 189, 115, 84, 148, 43, 19, 244, 208, 254, 242, 215, 150, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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