Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3ecf5819ec55a2cd35dfe18c04016ee3cc94fa73dfb43515353d46e79274a4b

Tx prefix hash: c3db075eb2d00e7c0d5ef9a2f706abee4d38ec81a6e2246af06486266485d95a
Tx public key: c9b7a0aa9d8b80d7ce4daec2ccc9d87eb80a6b5fbaca8a2c324b3469c4e89a66
Timestamp: 1731402685 Timestamp [UCT]: 2024-11-12 09:11:25 Age [y:d:h:m:s]: 00:011:20:24:47
Block: 1151998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8478 RingCT/type: yes/0
Extra: 01c9b7a0aa9d8b80d7ce4daec2ccc9d87eb80a6b5fbaca8a2c324b3469c4e89a66021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 158a8363aa5028f71fd6ffb2fc69b546bccf6af3975fe157a2b1cde9a1858991 0.600000000000 1637589 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": 1152008, "vin": [ { "gen": { "height": 1151998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "158a8363aa5028f71fd6ffb2fc69b546bccf6af3975fe157a2b1cde9a1858991" } } ], "extra": [ 1, 201, 183, 160, 170, 157, 139, 128, 215, 206, 77, 174, 194, 204, 201, 216, 126, 184, 10, 107, 95, 186, 202, 138, 44, 50, 75, 52, 105, 196, 232, 154, 102, 2, 17, 0, 0, 0, 8, 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