Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd00581a756673bc59e9d737dce98a0c49584eec1463bf173364a57ce0cb051f

Tx prefix hash: c1c7b07d8aae90b566cc9351d8bbe9d7c7a16a02c32eb08b01e4e4a4ab34061c
Tx public key: d2b3c2696cf751b4f9800bfce3167862934be0b0659cc529f35f9da471dbad75
Timestamp: 1734560891 Timestamp [UCT]: 2024-12-18 22:28:11 Age [y:d:h:m:s]: 00:111:23:49:52
Block: 1178185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79802 RingCT/type: yes/0
Extra: 01d2b3c2696cf751b4f9800bfce3167862934be0b0659cc529f35f9da471dbad7502110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 443e8b6c7e5ff1555fc0b12c90f7af522ce37dcb334487c8beb9267da31af07a 0.600000000000 1664570 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": 1178195, "vin": [ { "gen": { "height": 1178185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "443e8b6c7e5ff1555fc0b12c90f7af522ce37dcb334487c8beb9267da31af07a" } } ], "extra": [ 1, 210, 179, 194, 105, 108, 247, 81, 180, 249, 128, 11, 252, 227, 22, 120, 98, 147, 75, 224, 176, 101, 156, 197, 41, 243, 95, 157, 164, 113, 219, 173, 117, 2, 17, 0, 0, 0, 13, 0, 127, 151, 138, 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