Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7f55642f2a8b18d1ef845de7dc46ec3451b5a320be3fac0bf6f3fd97b6dcce4

Tx prefix hash: 3a6437d45677e225ed975f59b28c7f1e789d454ebea1f4851d0597efbe076758
Tx public key: 6625a9679a2a7a722c83f892eb4693c83b47d022dc75b343ee09f59c61698cd1
Timestamp: 1708050241 Timestamp [UCT]: 2024-02-16 02:24:01 Age [y:d:h:m:s]: 01:056:15:54:46
Block: 958476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301544 RingCT/type: yes/0
Extra: 016625a9679a2a7a722c83f892eb4693c83b47d022dc75b343ee09f59c61698cd102110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fe8b03ea3dd39cfd469681462a8514814fcd4f35ab98d165d9ed96dc13a213b 0.600000000000 1417835 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": 958486, "vin": [ { "gen": { "height": 958476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fe8b03ea3dd39cfd469681462a8514814fcd4f35ab98d165d9ed96dc13a213b" } } ], "extra": [ 1, 102, 37, 169, 103, 154, 42, 122, 114, 44, 131, 248, 146, 235, 70, 147, 200, 59, 71, 208, 34, 220, 117, 179, 67, 238, 9, 245, 156, 97, 105, 140, 209, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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