Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1787c474c9f7a4a94b11a7e5a22ccc372d302a8ab501f5e5d016789e0ba62402

Tx prefix hash: 972b8334945769e79c5b22997ab90679efebac4c8934c45046bfc6fd70b5d44b
Tx public key: 7b2b740905e99665ebe3a92df9a071bf9af768f1010657fa02ac96dd0a7ba0c2
Timestamp: 1696478761 Timestamp [UCT]: 2023-10-05 04:06:01 Age [y:d:h:m:s]: 01:178:10:31:09
Block: 862755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388566 RingCT/type: yes/0
Extra: 017b2b740905e99665ebe3a92df9a071bf9af768f1010657fa02ac96dd0a7ba0c2021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.849834928000 dcy

stealth address amount amount idx
00: 0fff4fb6eec81522de70cc98f2d58c60f243fa99763508b60081393746012480 0.849834928000 1317191 of 0

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": 862765, "vin": [ { "gen": { "height": 862755 } } ], "vout": [ { "amount": 849834928, "target": { "key": "0fff4fb6eec81522de70cc98f2d58c60f243fa99763508b60081393746012480" } } ], "extra": [ 1, 123, 43, 116, 9, 5, 233, 150, 101, 235, 227, 169, 45, 249, 160, 113, 191, 154, 247, 104, 241, 1, 6, 87, 250, 2, 172, 150, 221, 10, 123, 160, 194, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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