Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: effdf545bbd0b060c6ce9222fb876ddde22d9b79ba2e3371071b49d618276965

Tx prefix hash: fa6beba0433c8ff925e5d9e2d2e57b193d0a8cffe8feab6185ac20da12c2ec2a
Tx public key: 64c11dda629eac55a28cc279385ecb3365db7a1455c51a553d96e8c87d0b23f3
Timestamp: 1731856357 Timestamp [UCT]: 2024-11-17 15:12:37 Age [y:d:h:m:s]: 00:213:21:01:20
Block: 1155759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152575 RingCT/type: yes/0
Extra: 0164c11dda629eac55a28cc279385ecb3365db7a1455c51a553d96e8c87d0b23f302110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ac1a05df1a454f27a7eed100931990058fbc2eb57a8df9d8c7c959721a2af89 0.600000000000 1641378 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": 1155769, "vin": [ { "gen": { "height": 1155759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ac1a05df1a454f27a7eed100931990058fbc2eb57a8df9d8c7c959721a2af89" } } ], "extra": [ 1, 100, 193, 29, 218, 98, 158, 172, 85, 162, 140, 194, 121, 56, 94, 203, 51, 101, 219, 122, 20, 85, 197, 26, 85, 61, 150, 232, 200, 125, 11, 35, 243, 2, 17, 0, 0, 0, 12, 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