Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09357a5940a0104d04bea6e19e762cec3c6930c5ba3e7a27ee451da805fd1758

Tx prefix hash: 3cdd43b95d7fe3a2e7c859e67d203f520ac6a4b88bc4b5eeecb01c26d647bb69
Tx public key: ed7123294328be04a5288f2df0edad63d2378a26dc9f00f5ea18133067615cb2
Timestamp: 1709156637 Timestamp [UCT]: 2024-02-28 21:43:57 Age [y:d:h:m:s]: 01:022:22:22:47
Block: 967656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277403 RingCT/type: yes/0
Extra: 01ed7123294328be04a5288f2df0edad63d2378a26dc9f00f5ea18133067615cb2021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b546c08d5fc61ee5571ae25aa9e9f14c56020502c91920d7151c2c2c2659f2c 0.600000000000 1427439 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": 967666, "vin": [ { "gen": { "height": 967656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b546c08d5fc61ee5571ae25aa9e9f14c56020502c91920d7151c2c2c2659f2c" } } ], "extra": [ 1, 237, 113, 35, 41, 67, 40, 190, 4, 165, 40, 143, 45, 240, 237, 173, 99, 210, 55, 138, 38, 220, 159, 0, 245, 234, 24, 19, 48, 103, 97, 92, 178, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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