Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f8d451474ebc2ed4edab8e781626b98092964a2a2217a18ebf0c8e5a99107a0

Tx prefix hash: b65c0538839d62c2b240a7d914b4a53f5832096a356d8dd43dff7f2ed9179ac3
Tx public key: 2ad2f3e8f973dd97e19c40ec4070f611fe6f1d3a583434c35b31240b46bd417a
Timestamp: 1704849617 Timestamp [UCT]: 2024-01-10 01:20:17 Age [y:d:h:m:s]: 01:330:20:27:15
Block: 931939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495313 RingCT/type: yes/0
Extra: 012ad2f3e8f973dd97e19c40ec4070f611fe6f1d3a583434c35b31240b46bd417a0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffd5abb629c0e203ba567e0208db086198c9733ce5a8cf1335eb790f4c37a96e 0.600000000000 1389847 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": 931949, "vin": [ { "gen": { "height": 931939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffd5abb629c0e203ba567e0208db086198c9733ce5a8cf1335eb790f4c37a96e" } } ], "extra": [ 1, 42, 210, 243, 232, 249, 115, 221, 151, 225, 156, 64, 236, 64, 112, 246, 17, 254, 111, 29, 58, 88, 52, 52, 195, 91, 49, 36, 11, 70, 189, 65, 122, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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