Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f13952cf15a8216e9fde567c9b60ec0e1d3687ae765273b82b7e46470a43ff5

Tx prefix hash: e7508f180f9b8fe44f06a4fd86eaf7ef31662917b5944c36c7767e39d3db857b
Tx public key: 8d59fa9e7a493af2169f64ad89ff00bc4b4299539c53bd6fb3c78dfbb611d276
Timestamp: 1706486326 Timestamp [UCT]: 2024-01-28 23:58:46 Age [y:d:h:m:s]: 00:352:16:16:42
Block: 945501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252487 RingCT/type: yes/0
Extra: 018d59fa9e7a493af2169f64ad89ff00bc4b4299539c53bd6fb3c78dfbb611d2760211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2be32770cf980e8403e97e9183ab7e5a4e6f611a9439a120d021ae8168030435 0.600000000000 1403815 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": 945511, "vin": [ { "gen": { "height": 945501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2be32770cf980e8403e97e9183ab7e5a4e6f611a9439a120d021ae8168030435" } } ], "extra": [ 1, 141, 89, 250, 158, 122, 73, 58, 242, 22, 159, 100, 173, 137, 255, 0, 188, 75, 66, 153, 83, 156, 83, 189, 111, 179, 199, 141, 251, 182, 17, 210, 118, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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