Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ed4d03a3dfdad055403b80b7b240a69e32b429a348b85375bc89b90646c30f3

Tx prefix hash: 84729d02aa14a5450c9759054b7a2eaaeef42cdfb7fd308eaecb03fc56a836be
Tx public key: a1f197f4d373add8f746bf618246d37329200431ae8ca844bdfdfa796ce766f0
Timestamp: 1734629258 Timestamp [UCT]: 2024-12-19 17:27:38 Age [y:d:h:m:s]: 00:105:08:36:56
Block: 1178753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75052 RingCT/type: yes/0
Extra: 01a1f197f4d373add8f746bf618246d37329200431ae8ca844bdfdfa796ce766f002110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d910664a950bfab214d0a5691f0d4a022704428c2df310e52acb7fcd42ea31ed 0.600000000000 1665142 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": 1178763, "vin": [ { "gen": { "height": 1178753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d910664a950bfab214d0a5691f0d4a022704428c2df310e52acb7fcd42ea31ed" } } ], "extra": [ 1, 161, 241, 151, 244, 211, 115, 173, 216, 247, 70, 191, 97, 130, 70, 211, 115, 41, 32, 4, 49, 174, 140, 168, 68, 189, 253, 250, 121, 108, 231, 102, 240, 2, 17, 0, 0, 0, 11, 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